home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Cream of the Crop 11
/
Cream of the Crop 11-1.iso
/
lan
/
3c589x.zip
/
3C589X.EXE
/
NDIS
/
3NET_LOG.TXT
next >
Wrap
Text File
|
1995-08-10
|
4KB
|
81 lines
3Com Corporation
3NET_LOG Utility Program Description
The \NDIS\OS2 directory of the EtherLink III LAN PC Card EtherDisk
contains the NDIS driver for OS/2. This directory also contains the
program 3NET_LOG.EXE which is a support utility for the OS/2 driver.
The utility program can be run from the OS/2 command prompt, and will
display messages indicating any events that the driver has detected since
it was loaded.
The EtherLink III LAN PC Card driver itself can display messages
only during initialization when it is first loaded. The actual start-up
of the card, including selection of the I/O Address and Interrupt, occurs
after the time when messages can be displayed. The PC Card environment
also adds the possibility of the card being removed and reinserted. The
3net_log program provides a method of discovering the card configuration
and any events that the driver has detected.
If the ELPC3.OS2 driver is installed in an OS2 2.1 machine using the
workstation installation program from LanServer 3.x (described in the
LANSRV.TXT file on this diskette), the 3NET_LOG.EXE program will
automatically be copied into the IBMCOM directory on the workstation.
It is also possible to manually copy the program from the \NDIS\OS2
directory on this diskette.
If the network does not appear to be operating correctly, running the
3net_log program may lend some insight into possible causes. If the driver
for the EtherLink III LAN PC Card loads without error, but fails to
bind to the network protocol, or if everything loads correctly but the
workstation can't connect to the network, you may want to run 3net_log to
see if any unusual events have been logged.
To run the log-display program, follow these steps:
1. Open an OS/2 Command Line window or screen.
2. At the command line prompt, type:
\IBMCOM\3NET_LOG
3. The log program should display the Interrupt and IOBase that the driver
is using to access the card. If the driver is not bound to the protocol, the
values displayed may not be valid, but in that case they should both display
as zero.
4. Press a key to continue. The program will display any event log entries
that have been recorded by the driver. These events consist of the date and
time when the event occurred, followed by a message describing the event.
Two event messages are normal and indicate successful load and initialization
of the driver. They are:
Driver successfully loaded.
Driver Bound to Protocol.
Other normal messages include card insertion and removal events.
Following are the most likely unexpected events and their causes:
Driver could not become Card Services client. No Card Services found.
or
Driver could not link to Card Services.
-- Card Services or Socket Services may not be installed correctly
on this machine. Card Services is part of OS/2 2.1;
Socket Services should be provided by the PC vendor.
Driver could not register with Card Services. Timeout on registration.
-- The 3C589 was not in a socket when the driver loaded, or the
driver was not able to obtain needed resources from
Card Services.
Could not communicate with the 3Com ELPC3 driver.
Check to ensure the driver is being loaded in CONFIG.SYS.
-- Usually this is because the driver was never loaded. The
suggested action is included in the message.
(%VER NDIS - 3Net_Log Program v1.5a)